XML system

ABSTRACT

An XML system is configured to print bar code labels, tags, tickets, cards, or other media, and/or encode RFID devices embedded in media, based upon an extensible markup language (XML) input data stream. The XML system includes a computer system having a memory subsystem, a communication interface operatively coupled to a network, an XML processor configured to receive and process the XML input data stream, and an extensible stylesheet language transformation (XSLT) processor configured to either obtain a stylesheet identified in the XML data stream or obtain the stylesheet from a stylesheet repository. The XSLT processor transforms data in the XML input data stream into transformed XML data based upon the stylesheet obtained. Also included is an extensible stylesheet language formatting object (XSLFO) processor configured to format the transformed XML data into formatted XML data based upon XSLFO instructions contained in the stylesheet, and a rendering subsystem configured to receive the formatted XML data and generate a printable representation of the bar code label, tag, ticket, card, other media, and/or generate encoding information for an RFID device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/102,614, filed May 6, 2011, entitled “XML System”; which is acontinuation of U.S. application Ser. No. 11/561,084, filed Nov. 17,2006, now U.S. Pat. No. 7,959,082, entitled “XML System”; which is acontinuation of U.S. application Ser. No. 11/010,895, filed Dec. 13,2004, now U.S. Pat. No. 7,172,122, entitled “XML System”; which is acontinuation of U.S. application Ser. No. 10/601,213, filed Jun. 20,2003, now U.S. Pat. No. 6,908,034, entitled “XML System”; which is acontinuation-in-part of U.S. application Ser. No. 10/348,422, filed Jan.21, 2003, now U.S. Pat. No. 6,655,593, entitled “Native XML Printer”;which is a continuation of U.S. application Ser. No. 10/197,014, filedJul. 17, 2002, now U.S. Pat. No. 6,540,142, entitled “Native XMLPrinter”; which claims priority from U.S. Provisional Application No.60/345,389, filed Jan. 4, 2002, entitled “XML Printer Technology”, andU.S. Provisional Application No. 60/341,427, filed Dec. 17, 2001,entitled “Bar Code Labeling Systems Having Machine Readable Standards”,all of which are hereby incorporated herein in their entirety byreference.

STATEMENT REGARDING COPYRIGHT RIGHTS

A portion of this disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice Patent files or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The present invention relates generally to a method and apparatus forprinting media, such as tickets, tags, cards, barcode labels, sheet fedpaper, continuous and fan-folded paper, plastic media, and for encodingRF (Radio Frequency) identification circuitry (RFID) that may beembedded in media, and more specifically to a native printer that printssuch as printed media and/or encodes RFID devices based on an XML datastream.

BACKGROUND

Printer systems for printing barcodes and for transmitting data to abarcode printer are known. However, many such systems use proprietarymethods of data encoding, and therefore such methods cannot be usedinterchangeably with other barcode printers. Also, known data encodingmethods typically render the underlying data unreadable by humans. Whilethis presents no impediment to the computer systems, it may beburdensome to humans attempting to review, debug or understand certaindata appearing in the underlying barcode element names.

Barcode labeling is used extensively in many facets of commerce. Inparticular, packages or merchandise shipped from one destination toanother are identified by the shipper by a specific barcode label.Conversely, merchandise received may also be identified and entered intothe receiver's inventory system by use of the barcode label. Often, thereceiver of merchandise may dictate the form and content of the barcodeapplied by the shipper. This is referred to as “compliance labeling.” Ofcourse, merchandise need not be shipped to avail itself of the benefitsof barcode labeling. For example, inventory control systems makeextensive use of barcode labeling to track and monitor various goodswithin a facility or between facilities.

Compliance labeling is typically used by buyers of merchandise havingrelatively large market power or purchasing power. Because of theireconomic power, they may be able to dictate the form and content of thebarcode labels applied to products provided to them by their suppliersor vendors. Although this may be burdensome to the supplier, if thesupplier desires to do business with the buyer, they must comply withtheir demands with respect to labeling. For example, large retailers,such as Wal-Mart, Inc., not only have the ability and purchasing powerto require that suppliers meet their compliance labeling demands, butmay also fine suppliers who fail to comply with the labelingrequirements.

Further, such barcode labeling requirements may change at the whim ofthe entity demanding compliance. Accordingly, the supplier mustimplement the new labeling requirements and test the modified barcode toinsure that it meets all specifications. This is relatively inefficientand time consuming. It is also prone to errors, which may translate intomonetary fines.

A need exists to provide an open standard for defining barcode labelinginformation that is self-validating and which does not requiresignificant software programming changes to implement a change in formor content of a barcode label. A need also exists for use of a format inwhich to provide data to a barcode printer where the data isunderstandable by a human reading the data. Additionally, a need existsfor use of a format in which other data, such as RFID data, may besupplied to a device to effect encoding of the RFID data into embeddedRFID circuits or other automatic identification devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The features of the present invention which are believed to be novel areset forth with particularity in the appended claims. The invention,together with further objects and advantages thereof, may best beunderstood by reference to the following description in conjunction withthe accompanying drawings.

FIG. 1 is a high-level hardware block diagram of a specific embodimentof an XML system according to the present invention;

FIG. 2 is a high-level software block diagram of a specific embodimentof an XML system;

FIG. 3 is a combined high-level software block diagram and data flowdiagram of a specific embodiment of an XML system;

FIG. 4 is a high-level software block diagram of a specific embodimentof a bitmap/barcode and/or radio frequency identification (RFID)rendering engine;

FIG. 5 is a specific representation of a barcode label produced inaccordance with the XML system of FIGS. 1-4; and

FIG. 6 is a specific example of an alternate embodiment of an XML systemconfigured as a barcode and/or RFID rendering server.

DETAILED DESCRIPTION

In this written description, the use of the disjunctive is intended toinclude the conjunctive. The use of definite or indefinite articles isnot intended to indicate cardinality. In particular, a reference to“the” object or thing or “an” object or “a” thing is intended to alsodescribe a plurality of such objects or things.

Referring now to FIG. 1, a specific embodiment of a high-level hardwareblock diagram of an XML system 10 is shown generally. The XML system 10includes a computer or processing system 12, which includes varioushardware components, such as RAM 14, ROM 16, hard disk storage 18, cachememory 20, database storage 22, and the like (also referred to as“memory subsystem” 26), as is known in the art. The computer system 12may include any suitable processing device 28, such as a computer,microprocessor, RISC processor (reduced instruction set computer), CISCprocessor (complex instruction set computer), mainframe computer, workstation, single-chip computer, distributed processor, server,controller, micro-controller, discrete logic computer and the like, asis known in the art. For example, the processing device 28 may be anIntel Pentium® microprocessor, x86 compatible microprocessor, orequivalent device.

The memory subsystem 26 may include any suitable storage components,such as RAM, EPROM (electrically programmable ROM), flash memory,dynamic memory, static memory, FIFO (first-in first-out) memory, LIFO(last-in first-out) memory, circular memory, semiconductor memory,bubble memory, buffer memory, disk memory, optical memory, cache memory,and the like. Any suitable form of memory may be used whether fixedstorage on a magnetic medium, storage in a semiconductor device orremote storage accessible through a communication link.

A user interface 30 may be coupled to the computer system 12 and mayinclude various input devices 36, such as switches selectable by theuser and/or a keyboard. The user interface also may include suitableoutput devices 40, such as an LCD display, a CRT, various LED indicatorsand/or a speech output device, as is known in the art.

To communicate between the computer system 12 and external sources, acommunication interface 42 may be operatively coupled to the computersystem. The communication interface 42 may be, for example, a local areanetwork, as an Ethernet network, intranet, or other suitable network 43.The communication interface 42 may also be connected to a publicswitched telephone network (PSTN) 46 or POTS (plain old telephonesystem), which may facilitate communication via the Internet 44.Dedicated and remote networks may also be employed. Any suitablecommercially available communication device or network may be used, asis known in the art.

The computer system 12 may be further coupled to a printer system 50.The printer system 50 may include a media/paper control system 52, aprinter driver 54 and a print head mechanism 56. Any suitable printercapable of printing barcode labels may be used, which may includevarious dot matrix, ink jet, laser and/or thermal printers. Of course,dot matrix printers are usually of lower quality and require closermonitoring of the label output. Preferably, the printer system 50 is athermal transfer printer. Such suitable printers, for example, areavailable from Zebra Technologies Corporation of Vernon Hills, Ill., andmay include the Model Xi series barcode printers (XiIII+, 90XiIII,96XiIII, 140XiIII, 170XiIII, 220XiIII, etc.), the 2800 Series barcodeprinters, Model Z4M, Z6M, 105SL barcode printers, and others. Anysuitable barcode label printer may be used.

Alternatively, the printer system 50 may include a “non-printing”mechanism to handle the programming of RFID (radio frequencyidentification) media, which may also receive printed labeling or otherprinted indicia on its surface. The term “printer system” is meant toinclude systems that also include RFID capability although the “RFID”may not be part of the term. Additionally, although the term “barcodelabels” are used herein, this term is not limited to a paper label, andmay include, for example, tickets, tags, cards, sheet fed paper,continuous and fanfold paper, plastic media, media embedded with RFIDcircuits, and other automatic identification devices. The presentinvention applies to any type of media.

Typically, such printers may include various motors, label cutters,ribbon handlers, sensors, and the like (not shown). Additionally, suchprinters may include various control inputs or sensors, such as a mediasensor, print head temperature sensor, head open sensor, ribbon sensor,and the like (not shown), as is known in the art. The printer system 50may include one or more additional processors 60, other than theprocessor 28 residing in the computer system 12. Alternatively, theprocessor 28 in the computer system 12, if sufficiently powerful, maycontrol and handle the printer system 50 functions without the need fora separate processing device. Thus, all functions of the printer system50 may be controlled by a computer or processor physically separate fromthe printer system.

The processor 60 of the printer system may be further operativelycoupled to an RFID transceiver 61. The RFID transceiver 61 may beoperatively coupled to the processor 60 or may be operatively coupled tothe processing device 28 of the computer system 12, as shown by a dashedline in FIG. 1. It is not important to the scope of this invention wherethe RFID transceiver 61 resides or to which processing component it iscoupled.

The RFID transceiver 61 is configured to communicate with an RFIDtransponder 62 and program the RFID transponder. RFID transponder 62 maybe of the “chip” or “chipless” type, and one common form of such an RFIDtransponder, which is often used in “smart labels,” includes an antennaand an RFID integrated circuit (not shown). Such RFID transponders 62include both DC powered active transponders and battery-less passivetransponders, and are available in a variety of form factors. The term“barcode printer” or “barcode system” is used interchangeably hereinwith the term “barcode/RFID system,” “XML system” and the like, and sucha system includes the capability to encode RFID data into an RFIDtransponder, even though the term “RFID” may not necessarily be part ofthe identifying text. The system 12 must have the capability to encodeRFID data into an RFID transponder.

Greater detail concerning RFID transponders may be found in applicationSer. No. 10/001,364, entitled Method And Apparatus For Associating OnDemand Certain Selected Media And Value-Adding Elements, filed Oct. 25,2001, and currently pending, which is owned by the assignee of thisapplication. Application Ser. No. 10/001,364 is hereby incorporated byreference in its entirety.

Preferably, the computer system 12 and the printer system 50 are locatedin a common enclosure, but need not necessarily be constructed in thismanner. For example, the computer system 12 may be housed in anenclosure separate and apart from the printer system 50.

Referring now to FIGS. 1-3, FIG. 2 illustrates a specific embodiment ofa high-level software block diagram, while FIG. 3 illustrates a specificembodiment of a combined high-level software block diagram and data flowdiagram. The software described below may be executed by the processor28 of the computer system 12 of FIG. 1. Again, the processor 28 mayperform functions common to both the computer system 12 and the printersystem 50. There may be one or more processors, which may function inconcert or which may function separately. It is not material to thescope of this invention whether the processing or processing functionsare performed by or in the computer system or by or in the printersystem.

The software blocks illustrated in FIGS. 2-3 include an XML (extensiblemark-up language) processor 70 (also referred to as the “XML parser”),an XSLT (extensible stylesheet language transformation) processor 74, anXSLFO (extensible stylesheet language formatting object) processor 78, abit map/barcode/RFID rendering engine 80, the RFID transceiver 61, andthe printer driver 54 (FIG. 1). Of course, the RFID transceiver 61 maybe used in conjunction with printed labels, or may be used separately.The function and basic structure of the XML system 10 is unaffected bythe inclusion or non-inclusion of the RFID transceiver.

Note that the printer driver 54 is an example of a component describedabove whose function may be performed by either the processing device inthe computer system 12 or the processing device 60 (FIG. 1) in theprinter system 50, depending upon the physical location of theassociated processing device. Again, a single processing device, ifsufficiently powerful, may handle all functions for the XML system 10.

An XML schema repository 82 (schema repository) may provide input to theXML processor 70 while an XSLT stylesheet repository 84 (stylesheetrepository) may provide input to the XSLT processor 74. Also shown is anenterprise resource planning (ERP) system 88, which may be, for example,a warehouse management system that transmits an XML input data stream 90to the XML processor 70. The ERP system 88 essentially initiates therequest to print the barcode label or encode the RFID data into the RFIDtransponder 62, and provides the XML data that forms the bar code, RFIDencoded data, and other variable label or element fields to be printedor encoded. Such variable label fields may include, for example, any orall of the human-readable text and/or characters printed on the label.Of course, any enterprise computer system may be used, and thisinvention is not limited to use with any specific type of enterprisecomputer system.

When referring to the XML data, two basic types shall be referred toherein, namely, the XML value data and the XML element name. The XMLvalue data is the changeable data or the data that is desired to beprinted on the barcode label or encoded into the RFID transponder, suchas the data “1122 Green Street,” which may be part of the XML value datacorresponding to, for example, a shipping address. The XML element namesare part of the XML language semantics where an arbitrary label orelement name may be selected to represent the XML value data, the use ofwhich is defined by the XML language. Typically, the element namesappear between angled bracket (“<element name>”).

As described above, known barcode label and other automaticidentification systems often use proprietary software encoding schemes.Additionally, such schemes are often prone to errors, and the underlyingvalue data is usually unreadable by a non-technical individual. In knownsystems, if an error exists in the underlying value data sent from theenterprise system, or if the data is missing or otherwise incorrect, thebarcode system will print or encode what it is instructed to do, whichof course, produces an error in the barcode label or RFID transponder,rendering it inaccurate or useless.

Moreover, when dealing with compliance labeling, known systems requirenon-trivial changes in the data encoding when the form or content of thelabel changes in accordance with the compliance label demands. Suchchanges in the form or content of the barcode or RFID transponder,again, are susceptible to errors, which in turn can lead to monetaryfines by the entity demanding compliance. Business relationships mayalso be damaged by continued problems in the barcode labeling system,especially if such errors disrupt the business of the compliancedemander.

The present XML system 10 utilizes an open format. In particular, theformatting requirements and the form of the barcode label or RFIDtransceiver are all defined in the XML language. Moreover, not only isXML well defined and available for all to use, but non-programmers canunderstand the data and commands in an XML data stream or file (or hardcopy) with minimal training.

Various XML software blocks shown in FIGS. 2-3 are commerciallyavailable. Several different commercially available XML processors 70may be used interchangeably or with little modification. For example,the following commercially available XML processors 70 may be used: “XMLfor C++” available from IBM Corporation, “MSXML3” available fromMicrosoft Corporation, “Oracle XML Developers Kit for C” available fromOracle Corporation, “Expat” available from That Open Source SoftwareCenter, Ltd., or “Xerces-C++” available from the Apache SoftwareFoundation. However, any suitable XML processor may be used.

Similarly, several different commercially available XSLT processors 74may be used interchangeably or with little modification. For example,the following XSLT processors 74 may be used: “iXSLT” available fromInfoteria Corporation, “MSXML3” available from Microsoft Corporation,and “Libxslt” available from Gnome. However, any suitable XSLT processormay be used.

Again, several different commercially available XSLFO processors 78 maybe used interchangeably or with little modification. For example, thefollowing XSLFO processors 78 may be used: “XEP” available from RenderXCorporation, “XSL Formatter” available from Antenna House Corporation,and “FOP” available from the Apache Software Foundation. However, anysuitable XSLFO processor may be used.

Still referring to FIGS. 1-3, the XML processor 70 receives the XMLinput data stream 90 from an external source 88. For example, theexternal source may be the ERP system 88, such as the warehousemanagement system. The XML processor 70 essentially parses and processesthe XML input data stream 90 and generates a set of nodes, which may bein a “tree” structure, as is known in the art. Each of the softwareprocessing blocks shown in FIGS. 2-3 act on the nodes of the “tree” toperform their required function. The underlying value data contained inthe XML input data stream 90 from the ERP system 88 is processed andentered into a “label values node tree,” 100 which holds the data.

The following is a brief overview of the operation of the varioussoftware components. First, note that the XML input data stream 90includes text that identifies the name and location of other requiredXML documents or files. One such document is referred to as “XML schema”or “schema.” The schema is used to validate the XML input data stream,including the underlying value data. If validation is successful, astylesheet is applied, as will be described below. The name and locationof the stylesheet is also specified in the XML input data stream 90.Application of the stylesheet is handled by the XSLT processor 74, whichunder the direction of the stylesheet, may transform the underlying XMLelement names and/or underlying value data. Next, the data is processedby the XSLFO processor 78, which handles formatting and “layout” of theunderlying value data, which may include, for example, formatting theunderlying value data in accordance with, for example, font type, fontsize, color, and the like. Next, the underlying value data is processedby the bitmap/barcode/RFID rendering engine 80, which creates a bitmap92 of the barcode label or the programming code sequence for the RFIDtransponder corresponding to the transformed and formatted data. Therendering engine 80 may utilize an “instream foreign object” residing inthe stylesheet to direct creation of the bitmap. The bitmap 92 is thensent to the printer driver 54 (FIG. 1) for subsequent printing of thebarcode label by the barcode printer or to the RFID transceiver 61 forencoding into the RFID transponder 62 (FIG. 1).

As described above, the schema functions to validate the entire inputdata stream 90, in particular, the underlying value data, where errorsmay be typically found. In practice, errors are often inadvertentlyintroduced when changes are made to the form or content of the bar codelabel.

The name and location of the schema document is contained in the XMLinput data stream 90, which XML input data stream corresponds to therequest to print and/or encode a barcode label. The XML processor 70 inconjunction with a schema validation module 110 validates the underlyingvalue data. The use of schema is cost effective because it preventserrors and omissions with respect to the final output, namely, the barcode label, or “shipping label,” or RFID tag or transponder.

If the XML input data stream 90 is rejected or flagged as having anerror, an error message may be transmitted back to the source 88. Thismay flag or trigger human intervention to correct the error. Forexample, in this specific example, the source is the ERP system 88. Inthis way, the data is initially checked prior to processing to ensurethat it complies with all required label and barcode rules.

This may be particularly beneficial when dealing with compliancelabeling. In known systems, the compliance demander would merely notifythe supplier as to the changes in the compliance labeling requirements.If the supplier then makes an error in interpreting or implementingthese changes or instructions, the labels produced or RFID transpondersencoded and applied to products shipped to the compliance demander mayhave errors, which could jeopardize future business or cause monetaryfines to be applied.

In the present invention, the compliance demander preferably makes thechanges directly to the schema and/or the XSLT stylesheet. For example,if the physical layout of the label has been changed or if element nameshave been changed, the compliance demander will modify the XSLTstylesheet. Similarly, if the underlying value data has been added ordeleted or otherwise qualified (i.e., a new acceptable numerical rangefor a zip code), the compliance demander may modify the schema. In thisway, the supplier need only modify the output of its ERP system 88 toensure that it matches the modified XML input data stream 90. If onlythe physical layout of the label has changed, the supplier does not needto make any modifications at all.

For example, the compliance demander may now require that a nine digitzip code be used rather than the original five digit zip code.Accordingly, the compliance demander may modify the schema to requireboth a first and second zip code field, and the second field will alsobe limited to numerical digits within a certain range, perhaps0000-9999. The compliance demander may also modify the stylesheet toaccommodate that change. In response thereto, the supplier must insertthe added zip code field in its ERP system so that it appears in the XMLinput data stream 90 sent to the XML system 10. If such modification ofthe XML input data stream 90 is not performed correctly, the schema willcause an error to be reported back to the ERP system 88, and the labelwill not be printed or the RFID transponder will not be encoded.

Thus, the supplier need only access the modified schema and/orstylesheet from the repository 82, 84, which is automatically applied tothe underlying value data when received. Essentially, minor changes, andsignificantly, major changes, to the form and content of the barcodelabel or RFID transponder are transparent to the supplier, and suchchanges to the content of the barcode label or RFID transponder arevalidated in accordance with the schema. Accordingly, the supplier neednot incur costs to change the form or content of the barcode label orRFID transponder dictated by the compliance demander, and cannot makeany errors in implementing such changes. If there are any errors, sucherrors would have been inadvertently made by the compliance demander,who could not then blame the supplier.

The schema documents are preferably obtained from the XML schemarepository 82. In one specific embodiment, the schema repository 82 maybe external to the XML system 10 and the computer system 12, and may beaccessed via the network, the Internet, or via any suitable network 43,44 to which the computer system is coupled. The schema repository 82 maycontain a plurality of schema documents. Thus, the XML input datastreams 90 representing the various requests to create a barcode labelor RFID transponder may each specify the name and location of thecorresponding schema in the repository 82. When the request is receivedby the XML processor 70, the corresponding schema may be retrieved fromthe schema repository 82.

In another embodiment, the schema obtained from the schema repository 82via the network 42, 43 may be kept locally, and thus may temporarilyreside in the memory subsystem 26 (FIG. 1), such as the hard disk 18 ordatabase 22. In this way, if the same schema is used for multiple XMLinput data streams 90 or for subsequent barcode label requests, the XMLprocessor 70 need not retrieve the same schema externally via thenetwork 42, 44, but rather, may retrieve that schema from the memorysubsystem 26, which may be more efficient. According to this embodiment,the compliance demander may change or modify the schema in the externalrepository 82 at only certain times. For example, the compliancedemander may change the stylesheet only at 1:00 AM each day. Thus, thesupplier need only update the schema from the repository 82 into thememory subsystem 26 only once per day, for example, after the compliancedemander has performed the schema update. The supplier would then knowthat the schema saved temporarily in the memory subsystem 26 is the mostrecent schema document, at least up until the time that the updating isscheduled to occur.

Regardless of the location from where the schema is obtained, the schemavalidation module 110 performs the checking and validation of theunderlying data. Although the schema validation module 110 is shown as aseparate block from the XML processor 70 in FIG. 2, it is shown in thislocation for purposes of illustration only so that it may be shown onthe drawing adjacent to the label values node tree 100, which is thedata upon which it acts. However, the schema validation module 110 maybe part of and integrated into the XML processor 70, or it may beseparate and apart therefrom.

Of course, the schema is also an XML document, and thus it is alsoprocessed by the XML processor 70. Accordingly, the result of theprocessing of the schema is the XML schema node tree 114 shown in FIG.3, which is the “memory representation” or working model of the schemathat was processed. The XML schema node tree 114 may be in the form of a“document object model” (DOM), as is known in the art. Further, the XMLschema node tree 114 may reside in cache memory for efficiency, as shownin an XML schema cache 116. The schema validation module 110 and/or theXML processor 70 operate on the data in the XML schema node tree 114 toperform its function of validating the underlying value data inaccordance with the schema document.

As described above, if an error exists in the XML input data stream 90,as determined by application of the schema, an error message may begenerated. If the XML input data stream 90 is validated, the dataremains essentially “untouched.” The data in the label value node tree100 is then processed by the XSLT processor 74 using the XSLTstylesheets.

Alternatively, validation of the underlying value data may be performedaccording to Document Type Definition (DTD) format, rather than use ofschema. Use of DTD is specified in detail in various XML specifications,and is known in the art.

The stylesheet documents are preferably obtained from the XSLTstylesheet repository 84. In one specific embodiment, the stylesheetrepository 84 may be external to the XML system 10 and the computersystem 12, and may be accessed via the network, the Internet, or via anysuitable network 43, 44 to which the computer system is coupled. Thestylesheet repository 84 may contain a plurality of stylesheets. Thus,XML input data streams 90 representing the various requests to create abarcode label or encode an RFID transponder may each specify the nameand location of the corresponding stylesheet in the repository 84. Whenthe request is received by the XML processor 70, the correspondingstylesheet may be retrieved from the stylesheet repository 84.

In another embodiment, the stylesheet obtained from the stylesheetrepository 84 via the network 43, 44 may be kept locally, and thus maytemporarily reside in the memory subsystem 26 (FIG. 1), such as the harddisk 18 or database 22. In this way, if the same stylesheet is used formultiple XML input data streams 90 or for subsequent barcode label orRFID transponder requests, the XML processor 70 need not retrieve thesame stylesheet externally via the network 43, 44, but rather, mayretrieve that stylesheet from the memory subsystem 26, which may be moreefficient.

According to this embodiment, the compliance demander may change ormodify the stylesheet in the external stylesheet repository 84 at onlycertain times. For example, the compliance demander may change thestylesheet only at 1:00 AM each day. Thus, the supplier need only updatethe stylesheet from the stylesheet repository 84 into the memorysubsystem 26 only once per day, for example, after the compliancedemander has performed the stylesheet update. The supplier would thenknow that the stylesheet saved temporarily in the memory subsystem 26 isthe most recent stylesheet, at least up until the time that the updatingis scheduled to occur.

Of course, the stylesheet is also an XML, document, and thus it is alsoprocessed by the XML processor 70. Accordingly, the result of theprocessing of the stylesheet is the XSLT stylesheet node tree 120 shownin FIG. 3, which is the “memory representation” or working model of thestylesheet that was processed. The XSLT stylesheet node tree 120 may bein the form of a “document object model” (DOM), as is known in the art.Further, the XSLT stylesheet node tree 120 may reside in cache memoryfor efficiency, as shown in an XSLT stylesheet cache 126. The XSLTprocessor 74 operates on the data in the XSLT stylesheet node tree 120to perform its function of transforming the underlying value data orunderlying element names in accordance with the stylesheet.

Note that although the XSLT style sheet is shown as an input to the XMLprocessor 70 in FIG. 3, the XSLT processor 74 processes the stylesheet.It is initially provided to the XML processor 70 because all XMLdocuments are first processed and placed into the appropriate datastructure for subsequent processing.

The XSLT processor 74 may modify, reposition, and rearrange theunderlying value data or may add to the underlying value data or deletesome of the underlying value data. For example, under direction of thestylesheet, the underlying value data may be rearranged into tableformat or into columns. In particular, the stylesheet may add XSLFOformatting elements and attributes.

After the underlying value data in the label value node tree 100 hasbeen processed in accordance with the corresponding stylesheet, an XSLFOinstance node tree 130 is produced. Again, the XSLFO instance node tree130 may be in the form of a document object module, as is known in theart. The XSLFO instance node tree 130 contains XSLFO commands (layoutinstructions) that directs the XSLFO processor 78 with respect toformatting and layout. The XSLFO processor 78 then interprets the XSLFOcommands and applies such commands to the underlying value data so as toproperly format and layout the underlying value data. The XSLFOprocessor 78 produces the XSLFO area node tree 130, which represents thefinal output of formatting before rendering.

Turning now to FIG. 3 and a code segment shown immediately belowentitled “code segment 1 for an XML input data stream,” the code segment1 illustrates an XML input data stream 90 in hard copy, which may, forexample, be sent to the XML system 10 by the ERP or warehouse managementsystem 88. Line numbering has been inserted for purposes of illustrationonly and is not part of the code.

Code Segment 1 For An XML Input Data Steam 1 <?xml version=“1.0”encoding=“UTF-8”?> <?xml-stylesheet type=“text/xs1”  href=“D:\Projects\XML\Native\Docs\ShipLabels.xsl”?> <labels 5  xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”  xsi:noNamespaceSchemaLocation=   “D:\Projects\XML\Native\Docs\ShipLabels.xsd”>   <label>   <name>Albert Einstein</name> 10    <address>1234 RelativeWay</address>    <city>Princeton</city>    <state>NJ</state>   <zip>08540</zip>   </label> 15   <label>    <name>StevenHawking</name>    <address>5678 Black Hole Drive</address>    <city>LosAngeles</city>    <state>CA</state> 20    <zip>90007</zip>   </label>  <label>    <name>Richard Feynman</name>    <address>90 QuantumCircle</address> 25    <city>New York</city>    <state>NY</state>   <zip>10044</zip>   </label> </labels>

The XML input data stream identifies the schema document as“ShipLabels.xsd,” and that schema document may be found, in thisspecific example, in a directory called “DIProjects/XML/Native/Docs,” asshown at line 7 in code segment 1. Further, the XML input data streamidentifies the stylesheet document as “ShipLabels.xsl,” and thatstylesheet document may also be found in a directory called“a/Projects/XML/Native/Docs,” as shown at line 3 of the code segment 1.Of course, the schema document and the stylesheet document may belocated anywhere, for example, as identified by an Internet address.

This specific example shows the underlying value data and element namesfor three shipping labels to be printed. Each shipping label contains anXML element name defined between angular brackets as follows: <name>,<address>, <city>, <state> and <zip>. The value of the first elementname, <name>, is “Albert Einstein,” the value of the second elementname, <address>, is “1234 Relative Way,” the value of the third elementname, <city>, is “Princeton,” the value of the forth element name,<state>, is “NJ” and the value of the fifth element name, <zip>, is“08540.” This is the underlying value data.

Now turning to FIG. 3, code segment 1, and a code segment shownimmediately below entitled “code segment 2 for XML schema,” the codesegment 2 illustrates a specific example of an XML document in the formof the XML schema document specified in the XML input data stream ofcode segment 1. Line numbering has been inserted for purposes ofillustration only and is not part of the code.

Code Segment 2 For XML Schema 1 <?xml version=“1.0” encoding=“UTF-8”?><xs:schema       xmlns:xs=“http://www.w3.org/2001/XMLSchema”      elementFormDefault=“qualified”> 5    <xs:element name=“address”type=“xs:string”/>    <xs:element name=“city” type=“xs:string”/>   <xs:element name=“label”>       <xs:complexType>         <xs:sequence> 10             <xs:element ref=“name”/>            <xs:element ref=“address”/>             <xs:elementref=“city”/>             <xs:element ref=“state”/>            <xs:element ref=“zip”/> 15          </xs:sequence>      </xs:complexType>    </xs:element>    <xs:element name=“labels”>      <xs:complexType> 20          <xs:sequence>             <xs:elementref=“label”             maxOccurs=“unbounded”/>          </xs:sequence>      </xs:complexType>    </xs:element> 25    <xs:element name=“name”type=“xs:string”/>    <xs:element name=“state”>       <xs:simpleType>         <xs:restriction base=“xs:string”>             <xs:enumerationvalue=“CA”/> 30             <xs:enumeration value=“NJ”/>            <xs:enumeration value=“NY”/>          </xs:restriction>      </xs:simpleType>    </xs:element> 35    <xs:element name=“zip”>      <xs:simpleType>          <xs:restriction base=“xs:int”>            <xs:minInclusive value=“00000”/>            <xs:maxInclusive value=“99999”/> 40         </xs:restriction>       </xs:simpleType>    </xs:element></xs:schema>

As mentioned above, the schema is used to validate the underlying valuedata. This entails checking to determine that all required data ispresent, that no extraneous data is present, that the data present iswithin the specified ranges, and the like. Any suitable validationscheme may be specified in the schema, depending upon the application.The XML language is robust and code may be written to handle a vastmultitude of requirements.

For example, the schema document shown in code segment 2 above specifiesthat the underlying value data corresponding to the element name,<address>, must be a string, as defined in the XML Schema specification,as shown by line 5 in the code segment 2. The schema document alsospecifies that the underlying value data corresponding to the elementnames of <name>, <address>, <city>, <state>, and <zip> must also bepresent in the sequence indicated, as shown by lines 9-15 in the codesegment 2. Further, this specific schema document shown in the codesegment 2 specifies that the underlying value data corresponding to theelement name, <state>, must be one of three states, namely, “CA,” “NJ,”or “NY.” Of course, this is only an abbreviated example, and not allstates have been included for purposes of illustration only. The schemadocument shown in code segment 2 also specifies that the underlyingvalue data corresponding to the element name, <zip>, must be in therange from 00000 to 99999. If any of the above-mentioned schema criteriaare not met by the data in the XML input data stream, the schemavalidation module 110 will reject it, and will preferably return anerror message back to the source 88.

Now turning to FIG. 3, code segments 1-2, and a code segment shownimmediately below entitled “code segment 3 for an XSLT stylesheet,” thecode segment 3 shows a specific example of an XML document in the formof the XSLT stylesheet document specified in the XML input data streamof the code segment 1. Line numbering has been inserted for purposes ofillustration only and is not part of the code.

Code Segment 3 For An XSLT Stylesheet 1 <?xml version=“1.0”encoding=“UTF-8” ?> <xsl:transform version=“1.0”   xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”   xmlns:fo=“http://www.w3.org/1999/XSL/Format” 5   xmlns:bo=“http://www.zebra.com/2002/XSL/Barcode> <xsl:outputmethod=“xml” version=“1.0” indent=“yes” />   <xsl:templatematch=“labels”>    <fo:root>     <fo:layout-master-set> 10      <fo:simple-page-master master-name=“all-labels”>         <fo:region-body margin=“lin” />      </fo:simple-page-master>    </fo:layout-master-set>     <fo:page-sequencemaster-name=“all-labels”> 15      <fo:flow flow-name=“xsl-region-body”     font=“12pt Times”>       <xsl:apply-templates />      </fo:flow>    </fo:page-sequence>    </fo:root> 20   </xsl:template>  <xsl:template match=“label”>    <fo:block break-after=“page”>    <xsl:apply-templates select=“name” />     <xsl:apply-templatesselect=“address” /> 25     <fo:block font=“bold 14pt Times”text-align=“left”>      <xsl:apply-templates select=“city” />     <xsl:apply-templates select=“state” />     </fo:block>    <xsl:apply-templates select=“zip” /> 30     <fo:block>     <fo:instream-foreign-object>       <bo:barcode>        <bo:postnetinterpretation-line=“none”>         <xsl:value-of select=“zip” /> 35       </bo:postnet>       </bo:barcode>     </fo:instream-foreign-object>     </fo:block>    </fo:block> 40  </xsl:template>   <xsl:template match=“name”>    <fo:block font=“bold14pt Times” text-align=“left”>     <xsl:value-of select=“.” />   </fo:block> 45   </xsl:template>   <xsl:template match=“address”>   <fo:block font=“bold 14pt Times” text-align=“left”>     <xsl:value-ofselect=“.” />    </fo:block> 50   </xsl:template>   <xsl:templatematch=“city”>    <xsl:value-of select=“.” />   </xsl:template>  <xsl:template match=“state”> 55   <xsl:text>,</xsl:text>  <xsl:value-of select=“.” /> </xsl:template> <xsl:template match=“zip”>  <fo:block font=“bold 14pt Times” text-align=“left”> 60   <xsl:value-of select=“.” />   </fo:block> </xsl:template></xsl:transform>

As mentioned above, the stylesheet is used to transform the data. Inthis specific example, the stylesheet of the code segment 3 defines twotypes of namespace, namely, a “bo” type object, which is selected to bea “barcode-type object,” and an “fo” type object, which is selected tobe a formatting object, which was described above with respect to theXSLFO processor 78. This permits differentiation between the differentobjects, as is known in the art. The stylesheet may cause some data tobe transformed or even added. For example, the underlying value datafrom the XML input data stream of the code segment 1, namely “Einstein,“1234 Relative Way,” and the like, is inserted, as indicated by lines40-62.

This stylesheet also causes a variety of “fo” type elements to begenerated, which are designated as formatting elements or XSLFO objects.The XSLFO objects contain layout type commands that the XSLFO processor78 “understands” and processes. Note that all lines of code having aprefix of “fo” are not interpreted by the XSLT processor 74, but rather,are passed on to the XSLFO processor 78.

For example, line 21 of the code segment 3 shows <xsl: templatematch=“label”> followed by <fo:block break-after=“page”> on line 22.This is interpreted by the XSLFO processor 78 to put a “page break”between the three shipping labels specified in the code segment 1.Essentially a new shipping label is created due to the page break, witheach new shipping label containing the underlying value data specifiedin the code segment 1.

Further, this specific stylesheet specifies that an “instream foreignobject” is inserted, as shown at line 31. Line 31 is shown as<fo:instream-foreign-object> in conjunction with lines 31-37, whichdefine the instream foreign object. Note that the instream foreignobject is not processed by either the XSLT processor 74 or the XSLFOprocessor 78. Rather, the instream foreign object is passed to and isprocessed by the bitmap/barcode/RFID rendering engine 80. For example,lines 32-36 of the code segment 3 cause a <bo:barcode> element to beinserted that contains the definition of a “postnet” barcode element,which element will later be processed by the bitmap/barcode/RFIDrendering engine 80. At line 34, the XSLT processor 74 causes the zipcode from the XML input data stream to be inserted as the text of the<bo:postnet> element. Alternatively, although not shown in the code, anRFID type instream foreign object may define the encoding forprogramming an RFID transponder.

Now turning to FIG. 3, code segments 1-3, and a code segment shownimmediately below entitled “code segment 4 for an XSLT instance nodetree representation,” the code segment 4 shows a specific example of arepresentation of an XSLFO instance node tree 130 output produced by theXSLT processor 74 in conjunction with the stylesheet of code segment 3,which output is a representation of the XSLFO instance node treeprovided to the XSLFO processor 78. Line numbering has been inserted forpurposes of illustration only and is not part of the code.

Code Segment 4 For An XSLFO Instance Node Tree Representation 1 <?xmlversion=“1.0” encoding=“UTF-16” ?>   <fo:rootxmlns:fo=“http://www.w3.org/1999/XSL/Format”  xmlns:bo=“http://www.zebra.com/2002/XSL/Barcode”>   <fo:layout-master-set> 5     <fo:simple-page-mastermaster-name=“all-labels”>      <fo:region-body margin=“lin” />    </fo:simple-page-master>    </fo:layout-master-set>   <fo:page-sequence master-name=“all-labels”> 10     <fo:flowflow-name=“xsl-region-body”     font=“12pt Times”>      <fo:blockbreak-after=“page”>       <fo:block font=“bold 14pt Times” text-       align=“left”>Albert Einstein</fo:block>       <fo:blockfont=“bold 14pt Times”       text-align=“left”>1234 15          Relative Way</fo:block>       <fo:block font=“bold 14pt Times”text-        align=“left”>Princeton, NJ</fo:block>       <fo:blockfont=“bold 14pt Times” text-        align=“left”>08540</fo:block> 20      <fo:block>        <fo:instream-foreign-object>        <bo:barcode>          <bo:postnet interpretation-          line=“none”>08540</bo:postnet> 25         </bo:barcode>      </fo:instream-foreign-object>      </fo:block>     </fo:block>    <fo:block break-after=“page”> 30      <fo:block font=“bold 14ptTimes”      text-align=“left”>Steven       Hawking</fo:block>     <fo:block font=“bold 14pt Times” text-align=“left”>5678       BlackHole Drive</fo:block>      <fo:block font=“bold 14pt Times”text-align=“left”>Los 35       Angeles, CA</fo:block>      <fo:blockfont=“bold 14pt Times” text-       align=“left”>90007</fo:block>     fo:block>       <fo:instream-foreign-object> 40        <bo:barcode>        <bo:postnet interpretation-         line=“none”>90007</bo:postnet>        </bo:barcode>      </fo:instream-foreign-object> 45      </fo:block>     </fo:block>    <fo:block break-after=“page”>      <fo:block font=“bold 14pt Times”text-       align=“left”>Richard Feynman</fo:block> 50      <fo:blockfont=“bold 14pt Times” text-align=“left”>90       QuantumCircle</fo:block>      <fo:block font=“bold 14pt Times”text-align=“left”>New       York, NY</fo:block>      <fo:blockfont=“bold 14pt Times” text- 55       align=“left”>10044</fo:block>     <fo:block>       <fo:instream-foreign-object>        <bo:barcode>        <bo:postnet interpretation- 60         line=“none”>10044</bo:postnet>        </bo:barcode>      </fo:instream-foreign-object>      </fo:block>     </fo:block> 65   </fo:flow>   </fo:page-sequence>  </fo:root>

Two main portions of code segment 4 above are briefly described, namely,one portion beginning at line 4 with the code <fo:layout-master-set> anda second portion beginning at line 9 with the code <fo:page-sequencemaster-name=“all-labels”>. This portion of the code essentially defineswhat a barcode label will “look like” or how it will be “laid-out” andhow the underlying value data will appear in that lay-out.

With respect to formatting the underlying value data shown in codesegment 1, for example, the font attribute of “bold 14 pt Times” andtext-align=“left” shown in lines 12-13 will be applied to the underlyingvalue data of “Albert Einstein” so that when the barcode label isprinted, the name of “Albert Einstein” will be printed in 14 point Timesfont, and it will be aligned with the left margin of the barcode label.As is known in the art, may different kinds of formatting instructionsmay be specified, which will be interpreted by the XSLFO processor 78.

Further, this specific example of the representation of the XSLFOinstance node tree 130 contains an instream foreign object, as shown atlines 21-26 of the code segment 4, which instream foreign object may notbe processed by the XSLFO processor 78. Rather, the instream foreignobject may be passed to the bitmap/barcode/RFID rendering engine 80 forprocessing. Note that at this point in the processing, the XSLFOprocessor 78 does not “know” how to print a barcode label or encode anRFID transponder because barcode element types and RFID transponderelement types are not included in the XSLFO specification. Rather, onlythe text information, such as the underlying value data, namely,“Einstein,” “1234 Relative Way,” and the like, as shown in code segments1-2, could be printed on the barcode label as text. With respect tolabels, no actual barcode symbol would appear because the XSLFOprocessor 78 does not “know” how to produce a barcode symbol. The RFIDtransponder would not be encoded because the XSLFO processor 78 does not“know” how to encode a transponder.

The result of processing by the XSLFO processor 78 is an XSLFO area nodetree 140. Note that the instream foreign object shown in the codesegment 4 is not processed by the XSLFO processor 78, but rather, ispassed to the barcode/bitmap/RFID rendering engine 80 in one or morenodes of the XSLFO area node tree 140. The instream foreign objectelement is referred to as <bo:barcode> and is shown at lines 21-26 ofthe code segment 4. The barcode/bitmap/RFID rendering engine 80 receivesthe <bo:barcode> element and processes the code contained in that block.For example, the rendering engine 80 interprets lines 23-24, namely,<bo:postnet interpretation-line=“none”>08540<bo:postnet> as definingthis particular node as being a “postnet” barcode type of element. Manydifferent “types” of barcode symbols may be defined, as is defined bycorresponding industry standards, discussed below.

Alternatively, if the instream foreign object element relates to RFIDencoding, the rendering engine 80 would interpret the instream foreignobject according to specific standards governing the programming andencoding of the RFID transponder 62 (FIG. 2) by the RFID transceiver 61(FIG. 1). Like the elements and attributes of the XML data that specifyhow a barcode is to be printed, such elements and attributes can alsospecify the text and characteristics to be programmed into an RFID tag,such as the RFID transponder 62. Essentially, the rendering inaccordance with the RFID-type instream foreign object governs theoperation of the RFID transceiver 61 (FIG. 1). As such, radio frequencysignals are transmitted between the RFID transceiver and the RFIDtransponder to effect programming of the RFID transponder.

The operation of the RFID transceiver may be according to internationalstandards such as ISO/IEC or according to proprietary specificationsfrom vendors such as Texas Instruments (Tag-it) or Phillips (I•Code).For example, operation may be governed by the International Organizationfor Standardization (ISO) specification 15693 for vicinity cards, or byISO specification 14443 for proximity cards. ISO specification 15693describes the physical characteristics, the radio frequency power andsignal interface, and the anticollision and transmission protocol. Thetransmission protocol specification includes the requests and responsesto read, write, and lock the transponder. Note that the ISOspecification 15693 is a preferable applicable standard when RFID labeltags are involved.

The underlying value data to be printed as a barcode symbol is thenumerical data “08540,” as shown in line 24 of code segment 4, whichunderlying value data is the zip code associated with Albert Einstein'saddress shown in the code segment 1. In this specific example, only thezip code is transformed into the barcode symbol. Of course, any and allinformation may be transformed into a barcode symbol, depending upon theapplication. Also, in this specific example, the instream foreignobjects shown in the code segment 4 only relate to the three zip codesshown in the code segment 1. No other underlying value data istransformed into the barcode symbol in this example.

Also note that the XML system 10 need not necessarily contain the XSLTprocessor 74. In an alternate embodiment, the XSLT processor 74 or theequivalent thereof may be remotely located from the XML system 10 andmay be configured to transform XML data in the XML input stream andprovide the transformed data to the XML system. Accordingly, the XMLsystem 10 may receive and process the transformed XML data intoformatted XML data. Remote or “separate” processing equivalent to theprocessing typically handled by the XSLT processor may be based uponXSLFO instructions contained in stylesheets, which also need not residein or be directly accessible to the XML system 10.

Turning now to FIGS. 2-4 in conjunction with the code segment 4,additional detail concerning the barcode/bitmap/RFID rendering engine 80and the processing of the instream foreign objects will now be setforth. As described above, the rendering engine 80 processes each nodeof the XSLFO area node tree 140 generated by the XSLFO processor 78. Asis known in the art, the XSLFO area node tree 140 is represented inmemory as a document object model. Accordingly, multiple nodes mayexist. For example, one node may contain the instream foreign object,another node may contain associated element names, another node maycontain associated text data, another node may contain associatedattributes, and the like.

As shown in block 150 in FIG. 4, the nodes of the XSLFO area node tree140 are processed. In particular, the rendering engine 80 “knows” how torender or produce the actual barcode symbol or RFID transponder encodingdefined by the corresponding instream foreign object. Commerciallyavailable XSLFO processors do not “know” how to process such instreamforeign objects representing barcode symbols and RFID transponders, andthus are not able to produce or render barcode symbols or encode RFIDtransponders. Commercially available XSLFO processors may, however,render text in an acceptable manner and may even render certain types ofinstream foreign objects.

If a particular node does not contain an instream foreign object,meaning that it may contain, for example, text data, then this node maybe processed in a “standard” way by utilizing the processing power ofthe XSLFO processor 78 rather than the rendering engine 80, asillustrated in a block 154. In one embodiment, the non-instream foreignobject is provided “back” to the XSLFO processor 78, or the XSLFOprocessor is notified that a particular node in the XSLFO area node tree140 is suitable for processing by it.

Processing of a node in the XSLFO area node tree 140 containing anon-instream foreign object may be processed by the XSLFO processor 78,as described above. Of course, different commercially available XSLFOprocessors render text, for example, into different formats. Forexample, the XSLFO processor referred to as “XSL Formatter” availablefrom Antenna House Corporation, as described above, renders a node intoa WINDOWS “device-independent bitmap” format. The XSLFO processorreferred to as “CEP” available from RenderX Corporation, as describedabove, renders a node into “PDF” format, and the XSLFO processorreferred to as “FOP” available from the Apache Software Foundation, asdescribed above, may also render a node into “PDF” format.

Preferably, the XML system 10 utilizes the “FOP” XSLFO processor 78available from the Apache Software Foundation because this XSLFOprocessor may be configured to “call” a subroutine or other processingfunction when it encounters an instream foreign object that it is notcapable of processing. In particular, this XSLFO processor 78 may be setto call the rendering engine software block 80 described herein, tohandle the instream foreign object that it is not capable of processing.

Next, as shown in a block 160, if the node contains an instream foreignobject representing a barcode or RFID transponder, which is not capableof being processed by the XSLFO processor 78, the rendering engine 80checks to determine if the instream foreign object has a “namespace”specific to this XML system 10. For example, the rendering engine 80 maycheck to determine if the namespace associated with the instream foreignobject corresponds to the “Zebra corporation namespace.” The namespacenotation is known in the art. This is shown in line 3 of the codesegment 4 as “xmlns:bo=“http://www.zebra.com/2002/XSL/Barcode”>” Thus,as shown in the code segment 4, the namespace defined above is appliedto any elements having a “bo” prefix. Such elements having a “bo” prefixare then only available for processing by the rendering engine 80, which“bo” prefix type elements correspond to a barcode-type instream foreignobject. The XSLFO processor 78 will not “know” how to process suchelements.

If the instream foreign object is not associated with the propernamespace, it is passed back to the XSLFO processor 78, assuming that itis not a barcode type instream foreign object because the XSLFOprocessor may be able to process some limited number of instream foreignobjects. This is shown by arrow 162 from the block 160 to the block 154.Generally, however, instream foreign objects exist or are created forthe specific reason that the data associated with an instream foreignobject is very unique in nature (such as a barcode), and thus, manycommercially available or general purpose XSLFO processors cannotprocess them.

Note that the commercially available XSLFO processors mentioned hereinare not necessarily incapable of processing all instream foreignobjects. They are, however, incapable of processing instream foreignobjects corresponding to barcode symbols and RFID encoding.

Assuming that instream foreign object has the appropriate namespace, ablock 170 interprets the elements in the instream foreign object todetermine barcode type. For example, the instream foreign object isshown at lines 21-26 of code segment 4. More specifically, the barcodeelement having a prefix of “bo,” indicating the correct namespacecorresponding to a barcode, is shown to have a barcode type of“postnet,” as shown in lines 23-24 of the code segment 4, which appearsas <bo:postnet interpretation-line=“none”>08540</bo:postnet>. Note thatlines 41-42 of the code segment 4 show a similar barcode element foranother instream foreign object, namely, the next barcode label to beprinted, which corresponds to the address of “Steven Hawking” shown incode segment 1.

Any barcode type may be specified in the instream foreign objectdepending upon the application. The barcode type is based upon knownbarcode standards. For example, the barcode type is not limited to apostnet type of barcode symbol, and may be, for example, Industrial 2 of5,” “PDF 417,” “UPC,” and the like. The barcode “type” specifies thebasic structure of the barcode symbol to be printed, such as thethickness of the bars, the ratio of the thickness of the bars to thewidth of the space between bars, and the like. Each specific knownbarcode standard is concretely defined.

Next, after the barcode type has been ascertained from the instreamforeign object, the attributes of the instream foreign object areinterpreted to determine the barcode characteristics, as shown in ablock 176. The characteristics may modify the way in which the barcodesymbol is created. For example, one attribute of the “postnet” typebarcode may be seen at lines 23-24 of the code segment 4 as“interpretation-line=“none””. As is known in the art,“interpretation-line=“none”” means that no corresponding human readabletext is generated along with the specific barcode symbol. Anotherexample of an attribute associated with the barcode element may be theheight of the barcode symbol, which may also be specified in theinstream foreign object as an attribute.

Using the barcode type and the attributes obtained from the instreamforeign object, the rendering engine 80 then obtains the actual nodetext data to be converted into the barcode symbol, as shown in a block180. In this example, the actual barcode data is the zip code “08540,”as is shown between reverse angled brackets (>80540<) in line 24 of thecode segment 4. The physical conversion from the numerical data “80540”into the bitmap representing the lines or bars of the barcode symbol(for a linear barcode, for example) may be performed by softwareroutines contained in, for example, the barcode label printerscommercially available from Zebra Corporation. Such suitable barcodeprinters may be models Xi series barcode printers (90XiIII Plus, 96XiIIIPlus, 140XiIII Plus, 170XiIII Plus, 220XiIII Plus, etc.), the 2800Series barcode printers, model Z4M, Z6M, 105SL barcode printers, and thelike. Such software routines or “native algorithms” contained in barcodeprinters commercially available from Zebra Corporation are veryefficient, and thus the barcodes are rendered quickly.

Once the bitmap representing the barcode symbol has been generated bythe block 180, that bitmap is then placed into or merged with the“master” or “label” bitmap 184, which label bitmap represents the imageof the entire shipping label, as shown in a block 182. The shippinglabel contains the human readable text, other text or characters, andthe barcode symbol. Note that the aforementioned bitmaps may beseparate, i.e., bitmaps for text and a bitmap for the barcode symbol, orone master bitmap may be used or “populated” as processing progresses.In that regard, note that the tree or data structure upon which therendering engine 80 operates is referred to as the “XSLFO area nodetree,” meaning that it contains different “areas.” Such areas maycorrespond to different or individual bitmaps or bitmap portions.However, any number of suitable bitmap structures may be used. The exactstructure or configuration of the bitmap, or the number of bitmaps isnot relevant to the scope of the present invention.

For example, the XSLFO processor 78 when generating text, may place“its” text in one particular bitmap. Such text may correspond to thename “Albert Einstein” discussed above. Because this text will also beprinted on the shipping label along with the barcode symbol, the“master” or “label” bitmap 184 will contain all of the componentbitmaps. The final “master” bitmap 184 is then sent to the printerdriver 54 (FIG. 1) so that the shipping label may be printed.

Turning now to FIGS. 4-5, FIG. 5 is a representation 190 of the finaloutput of the above-described processing for the first barcode shippinglabel specified in code segment 1. The text data is rendered andformatted in accordance with the corresponding stylesheet, while the zipcode 192 is also rendered in the form of a barcode symbol by therendering engine 80, as described above. Note that for purposes ofillustration only, the font size or font type shown in FIG. 5 may not bethe same as that specified in the corresponding stylesheet shown in thecode segment 3.

Referring back to block 170, assuming that the instream foreign objecthas the appropriate namespace, if the instream foreign object is not abarcode type, then block 170 interprets the elements in the instreamforeign object to determine if it is an RFID type. Just like any barcodetype may be specified in the instream foreign object, as set forthabove, any RFID transponder type may be specified in the instreamforeign object as well, depending upon the application. The RFIDtransponder type is based upon known RFID standards. For example, theRFID type is not limited to an ISO 15693 type of RFID encoding, and maybe, for example, a Tag-it or I•Code type of RFID encoding, and the like.The RFID type specifies the basic structure of the RFID data to beencoded, such as the data storage capacity, data addressing scheme,transmit frequency, receive frequency, proprietary features such asserial numbering and data locking, and the like. Each specific knownRFID standard is concretely defined, as set forth above.

Next, after it has been determined that the instream foreign object isan RFID type, the attributes of the instream foreign object areinterpreted to determine the RFID transponder characteristics, as shownin a block 183. The characteristics may modify the way in which the RFIDtransponder is encoded, such as which block to write, whether towrite-protect (lock) the block, whether to re-try write failures,positioning of the tag under the transceiver antenna during programming,and the like.

Using the RFID transponder type and the attributes obtained from theinstream foreign object, the rendering engine 80 then obtains the actualnode text data to be converted into the RFID transponder encoding, asshown in a block 185. For example, the actual RFID encoding may be thezip code “08540,” which may be placed as ASCII characters in blocks 0and 1 of a Tag-it transponder (since each block of a Tag-it holds 4bytes of data). A Tag-it transponder can hold 8 blocks each with 4 bytesof data for a total of 32 bytes of user data The physical conversionfrom the numerical data representing the actual RFID encoded data intothe form suitable for encoding into the RFID transponder may beperformed by software routines contained in, for example, the printersand systems commercially available from Zebra Corporation.

For example, several barcode printer/encoders may be used, such as ModelR-140 and Model R402, and the like. Such software routines or “nativealgorithms” contained in systems commercially available from ZebraCorporation are very efficient, and thus the barcodes and RFIDtransponder encoding are rendered quickly.

Once the RFID transponder encoding has been generated by the block 185,an RFID-specific data structure is rendered, as shown in a block 187.This block renders the RFID-specific data structure to the RFIDtransponder using the native RFID printer algorithms, as describedabove, to control the RFID transceiver 61 (FIG. 1) to read and encodethe RFID transponder 62 (FIG. 2). This essentially “programs” the RFIDtransponder, much in the same way as a programmable memory device isprogrammed.

Referring now to FIG. 6, an alternate embodiment is shown. Likereference numbers are used to denote like structures. In this specificembodiment, the XML system 10 need not include or specifically utilizethe XML printer apparatus in all instances. In this embodiment, forexample, an external requestor 194 may desire to have an XML input datastream rendered into a bitmap so that it can print the barcode label,which may be done remotely. Alternately, the external requestor 194 mayrequest that an RFID transponder be encoded. Accordingly, the externalrequestor 194 may send a request to the XML server 200 over the Internetor other network 43, 44. The request may be in the same form as the XMLinput data stream described above with respect to FIGS. 1-3 and codesegments 1-4. The request may also be in the form of a protocol thatcontains XML data, such as SOAP (Simple Object Access Protocol) as isknown in the art.

In response, the computer system 12 of the XML server 200 may processthe XML input data stream. All of the same processing functionsdescribed above are carried out in this embodiment, except that withrespect to barcodes and the like, the bitmap is not sent to the printerdriver. Rather, the bitmap is converted to any suitable format, such as“JPEG” or “PNG” format, as is known in the art. The JPEG or PNG file isthen sent back to the external requestor 194, who then formats the JPEGor PNG file for the appropriate printer driver, and prints and/ordisplays the barcode label. With respect to RFID transponders, theencoded data may be sent back to the requestor in the form of a datafile. Any suitable form or format of data file may be used. Accordingly,the present invention may function as a barcode rendering server and/oran RFID rendering server, and need not necessarily directly perform theprinting or encoding functions. Alternatively, the output representationof the data, may be in Scalable Vector Graphic format (SVG), whichformat is defined by appropriate industry standards.

Specific embodiments of an XML system according to the present inventionhave been described for the purpose of illustrating the manner in whichthe invention may be made and used. It should be understood thatimplementation of other variations and modifications of the inventionand its various aspects will be apparent to those skilled in the art,and that the invention is not limited by the specific embodimentsdescribed. It is therefore contemplated to cover by the presentinvention any and all modifications, variations, or equivalents thatfall within the true spirit and scope of the basic underlying principlesdisclosed and claimed herein.

That which is claimed:
 1. A method comprising: receiving an ExtensibleMarkup Language (XML) data stream; identifying, by one or moreprocessors, an indicator of an encoding scheme of the XML data stream;transforming data in the XML data stream based upon a style sheet andthe encoding scheme, the data being transformed for subsequentgeneration of at least one of a printable representation of at least aportion of a media, or encoding information for an RFID device, basedthereon.
 2. The method of claim 1, wherein the stylesheet includes anextensible stylesheet language formatting object (XSLFO) for formattingdata within the XML data stream.
 3. The method of claim 1, furthercomprising: transforming the incoming data stream according to at leastone of a UTF-8 encoding scheme or UTF-16 encoding scheme.
 4. The methodof claim 1, wherein the XML data stream is received at a print server.5. The method of claim 1, wherein the stylesheet is contained in the XMLdata stream or the stylesheet is retrieved from a stylesheet repositorybased upon content of the XML data stream.
 6. The method of claim 1,wherein the stylesheet further includes extensible stylesheet languagetransformation (XSLT) instructions for transforming the data in the XMLdata stream.
 7. An apparatus comprising: one or more processorsconfigured to implement an Extensible Markup Language (XML) processormodule, wherein being configured to implement the XML processor moduleincludes being configured to: receive an XML data stream; identify anindicator of an encoding scheme of the XML data stream; transform datain the XML data stream based upon a style sheet and the encoding scheme,the data being transformed for subsequent generation of at least one ofa printable representation of at least a portion of a media, or encodinginformation for an RFID device, based thereon.
 8. The apparatus of claim7, wherein the stylesheet includes an extensible stylesheet languageformatting object (XSLFO) for formatting data within the XML datastream.
 9. The apparatus of claim 7, wherein the one or more processorsare further configured to transform the incoming data stream accordingto at least one of a UTF-8 encoding scheme or UTF-16 encoding scheme.10. The apparatus of claim 7, wherein the apparatus is received at aprint server.
 11. The apparatus of claim 7, wherein the stylesheet iscontained in the XML data stream or the stylesheet is retrievable from astylesheet repository based upon content of the XML data stream.
 12. Theapparatus of claim 7, wherein the stylesheet further includes extensiblestylesheet language transformation (XSLT) instructions configured totransform the data in the XML data stream.
 13. A non-transitorycomputer-readable medium having computer readable program code storedthereon, the program code being configured to, when executed, cause anapparatus to at least: implement an Extensible Markup Language (XML)processor module, wherein the program code configured to cause theapparatus to implement the XML processing module includes beingconfigured to cause the apparatus to: receive an XML data stream;identify an indicator of an encoding scheme of the XML data stream;transform data in the XML data stream based upon a style sheet and theencoding scheme, the data being transformed for subsequent generation ofat least one of a printable representation of at least a portion of amedia, or encoding information for an RFID device, based thereon. 14.The computer-readable medium of claim 13, wherein the stylesheetincludes an extensible stylesheet language formatting object (XSLFO) forformatting data within the XML data stream.
 15. The computer-readablemedium of claim 13, wherein the one or more processors are furtherconfigured to transform the incoming data stream according to at leastone of a UTF-8 encoding scheme or UTF-16 encoding scheme.
 16. Thecomputer-readable medium of claim 13, wherein the apparatus is receivedat a print server.
 17. The computer-readable medium of claim 13, whereinthe stylesheet is contained in the XML data stream or the stylesheet isretrievable from a stylesheet repository based upon content of the XMLdata stream.
 18. The computer-readable medium of claim 13, wherein thestylesheet further includes extensible stylesheet languagetransformation (XSLT) instructions configured to transform the data inthe XML data stream.